Systems and methods for selecting a calling card to be used in placing an outgoing call

ABSTRACT

A system and method for, on a mobile device having a plurality of communication lines on which outgoing calls may be made, providing a user interface for selecting a calling card to be used in making an outgoing call to a desired phone number. The method includes: associating each calling card in a set of at least one calling card with a communication line; and displaying on a display of the mobile device a line selection menu containing a plurality of card/line identifiers; wherein each card/line identifier is configured to uniquely identify a corresponding associated calling card and communication line combination

TECHNICAL FIELD

Embodiments described herein relate generally to mobile device applications, and more specifically to phone-equipped mobile devices that allow outgoing calls to be made by a user on a communication line selected from a plurality of communication lines.

BACKGROUND

Many modern mobile devices are multi-functional. They may be configured to allow users to engage in both electronic mail (“e-mail”) communications and telephone communications, for example. Additionally, it is common for a user to utilize the mobile device for different purposes. For example, a user may operate a single mobile device to engage in communications relating to both business and personal uses.

Phone-equipped mobile devices may be adapted to accommodate an Alternate Line Service (ALS) or similar multi-line service. With respect to these mobile devices, two or more phone numbers may be associated with a mobile device, with each phone number being associated with a different communication line. A user may wish to place an outgoing call on a specific communication line so that when the call is received by a receiving party, the phone number associated with that communication line will be identified on the receiving party's phone where “call display” (or “Caller ID”) functionality has been enabled on that phone. Use of multiple communication lines may also be useful for line-specific tracking purposes (e.g. to facilitate separate billing for calls relating to business and personal uses).

Typically, in mobile device applications, only one communication line is deemed to be “active” at any given time (although in some instances it is possible to have a call on multiple lines at once, as will be understood). Outgoing calls are placed on the active line until an alternate communication line is selected. Outgoing calls are generally initiated by a user from a call screen provided by an application (e.g. a phone application) residing and executing on the mobile device.

A user may have one or more calling cards available to which phone charges, such as long distance charges, may be charged. Such calling card(s), for example, may be intended to assist in managing calling expenses. For example, a user may have one card for personal use and one or more cards for work purposes (eg. for different branches of a business).

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of example embodiments described herein, and to show more clearly how they may be carried into effect, reference will now be made, by way of example, to the accompanying drawings in which:

FIG. 1 is a block diagram of a mobile device in one example implementation;

FIG. 2 is a block diagram of a communication subsystem component of the mobile device of FIG. 1;

FIG. 3 is a block diagram of a node of a wireless network;

FIG. 4 is a block diagram illustrating further aspects of the example mobile device of FIG. 1;

FIG. 5 is a chart illustrating exemplary data as may be stored in calling card records in the calling card database of FIG. 4;

FIG. 6 is a flowchart illustrating steps of a method of providing a user interface that facilitates user selection of a calling card/communication line combination in accordance with at least one embodiment; and

FIGS. 7A to 7D are examples of screenshots of a user interface provided to a user in accordance with an example implementation of one embodiment.

DETAILED DESCRIPTION

Users may wish to manage calling activity by communication line, with certain phone charges being charged to a particular calling card. It should be understood that reference to a “calling card” herein is not intended to require the presence of a physical “card”, but to the information typically associated therewith.

Embodiments described herein are generally directed to a system and method and user interface for providing ALS and calling card information to mobile device users and for facilitating the selection of an outgoing line and calling card in placing a call.

In a broad aspect, there is provided a method of, on a mobile device having a plurality of communication lines on which outgoing calls may be made, providing a user interface for selecting a calling card to be used in making an outgoing call to a desired phone number. The method includes: associating each calling card in a set of at least one calling card with a communication line; and displaying on a display of the mobile device a line selection menu containing a plurality of card/line identifiers; wherein each card/line identifier is configured to uniquely identify a corresponding associated calling card and communication line combination.

The method may further include providing the set of at least one calling card. In some configurations, the method may also include: selecting one of the card/line identifiers; receiving the desired phone number; and initiating an outgoing call in connection with the selected line identifier.

The method may also include: storing calling card data corresponding to each calling card. Such calling card data may correspond to each calling card and may comprise: a calling card phone number; and authentication data. The process of initiating the outgoing call may involve placing a call (on the communication line corresponding to the selected card/line identifier) to the calling card phone number corresponding to the selected card/line identifier. The corresponding authentication data may then be communicated over the communication line corresponding to the selected card/line identifier; and the desired phone number may also be communicated over the communication line corresponding to the selected card/line identifier.

A computer-readable medium may be provided which comprises instructions executable on a processor of the mobile device for implementing the method(s).

In another aspect, a mobile device may be configured to provide a user interface for selecting a calling card to be used in making an outgoing call to a desired phone number. Such mobile device provides access to a plurality of communication lines on which outgoing calls may be made and includes a processor, a display, and at least one input device. The processor is configured to execute an application programmed to perform the steps of the method(s).

Another aspect is directed towards a system for providing a user interface for selecting a calling card to be used in making an outgoing call to a desired phone number. The system includes: a plurality of communication lines on which outgoing calls may be made by a user, a processor, a display, and at least one input device. The processor is configured to execute an application programmed to perform the method(s).

In yet a further broad aspect, a mobile device is provided comprising a processor, a display, and at least one input device. The mobile device is configured to access a plurality of communication lines, and the processor is configured to perform the steps of: associating each calling card in a set of at least one calling card with a communication line; and displaying on the display a line selection menu containing a plurality of card/line identifiers. Each card/line identifier is configured to uniquely identify a corresponding associated calling card and communication line combination. The device may also include a calling card database configured to store calling card data corresponding to each calling card in the set.

The calling card data corresponding to each calling card may include: a calling card phone number; and authentication data. In some configurations, upon receiving input corresponding to a selection of one of the line identifiers and upon receiving a desired phone number, the processor may be further configured to place a call to the calling card phone number corresponding to the selected card/line identifier. Such call is placed on the communication line corresponding to the selected card/line identifier. The processor may also be configured to: communicate the corresponding authentication data over the communication line corresponding to the selected card/line identifier; and communicate the desired phone number over the communication line corresponding to the selected card/line identifier.

These and other aspects and features of various embodiments will be described in greater detail below.

Some embodiments described herein make use of a mobile station. A mobile station is a two-way communication device with advanced data communication capabilities having the capability to communicate with other computer systems, and is also referred to herein generally as a mobile device. A mobile device may also include the capability for voice communications. Depending on the functionality provided by a mobile device, it may be referred to as a data messaging device, a two-way pager, a cellular telephone with data messaging capabilities, a wireless Internet appliance, or a data communication device (with or without telephony capabilities). A mobile device communicates with other devices through a network of transceiver stations.

To aid the reader in understanding the structure of a mobile device and how it communicates with other devices, reference is made to FIGS. 1 through 3.

Referring first to FIG. 1, a block diagram of a mobile device in one example implementation is shown generally as 100. Mobile device 100 comprises a number of components, the controlling component being microprocessor 102. Microprocessor 102 controls the overall operation of mobile device 100. Communication functions, including data and voice communications, are performed through communication subsystem 104. Communication subsystem 104 receives messages from and sends messages to a wireless network 200. In this example implementation of mobile device 100, communication subsystem 104 is configured in accordance with the Global System for Mobile Communication (GSM) and General Packet Radio Services (GPRS) standards. The GSM/GPRS wireless network is used worldwide and it is expected that these standards will be superseded eventually by Enhanced Data GSM Environment (EDGE) and Universal Mobile Telecommunications Service (UMTS). New standards are still being defined, but it is believed that they will have similarities to the network behaviour described herein, and it will also be understood by persons skilled in the art that the invention is intended to use any other suitable standards that are developed in the future. The wireless link connecting communication subsystem 104 with network 200 represents one or more different Radio Frequency (RF) channels, operating according to defined protocols specified for GSM/GPRS communications. With newer network protocols, these channels are capable of supporting both circuit switched voice communications and packet switched data communications.

Although the wireless network associated with mobile device 100 is a GSM/GPRS wireless network in one example implementation of mobile device 100, other wireless networks may also be associated with mobile device 100 in variant implementations. Alternatively, the network and device 100 might employ WiFi/WiMax radios utilizing SIP (session initialization protocols) and VoIP (voice over internet protocols). Different types of wireless networks that may be employed include, for example, data-centric wireless networks, voice-centric wireless networks, and dual-mode networks that can support both voice and data communications over the same physical base stations. Combined dual-mode networks include, but are not limited to, Code Division Multiple Access (CDMA) or CDMA2000 networks, GSM/GPRS networks (as mentioned above), and future third-generation (3G) networks like EDGE and UMTS. Some older examples of data-centric networks include the Mobitex™ Radio Network and the DataTAC™ Radio Network. Examples of older voice-centric data networks include Personal Communication Systems (PCS) networks like GSM and Time Division Multiple Access (TDMA) systems.

Microprocessor 102 also interacts with additional subsystems such as a Random Access Memory (RAM) 106, flash memory 108, display 110, auxiliary input/output (I/O) subsystem 112, serial port 114, keyboard 116, speaker 118, microphone 120, short-range communications 122 and other devices 124.

Some of the subsystems of mobile device 100 perform communication-related functions, whereas other subsystems may provide “resident” or on-device functions. By way of example, display 110 and keyboard 116 may be used for both communication-related functions, such as entering a text message for transmission over network 200, and device-resident functions such as a calculator or task list. Operating system software used by microprocessor 102 is typically stored in a persistent store such as flash memory 108, which may alternatively be a read-only memory (ROM) or similar storage element (not shown). Those skilled in the art will appreciate that the operating system, specific device applications, or parts thereof, may be temporarily loaded into a volatile store such as RAM 106.

Mobile device 100 may send and receive communication signals over network 200 after required network registration or activation procedures have been completed. Network access is associated with a subscriber or user of a mobile device 100. To identify a subscriber, mobile device 100 requires a Subscriber Identity Module or “SIM” card 126 to be inserted in a SIM interface 128 in order to communicate with a network. SIM 126 is one type of a conventional “smart card” used to identify a subscriber of mobile device 100 and to personalize the mobile device 100, among other things. Without SIM 126, mobile device 100 is not fully operational for communication with network 200. By inserting SIM 126 into SIM interface 128, a subscriber can access all subscribed services. Services could include: web browsing and messaging such as e-mail, voice mail, Short Message Service (SMS), and Multimedia Messaging Services (MMS). More advanced services may include: point of sale, field service and sales force automation. SIM 126 includes a processor and memory for storing information. Once SIM 126 is inserted in SIM interface 128, it is coupled to microprocessor 102. In order to identify the subscriber, SIM 126 contains some user parameters such as an International Mobile Subscriber Identity (IMSI). An advantage of using SIM 126 is that a subscriber is not necessarily bound by any single physical mobile device. SIM 126 may store additional subscriber information for a mobile device as well, including datebook (or calendar) information and recent call information.

Mobile device 100 is a battery-powered device and includes a battery interface 132 for receiving one or more rechargeable batteries 130. Battery interface 132 is coupled to a regulator (not shown), which assists battery 130 in providing power V+ to mobile device 100. Although current technology makes use of a battery, future technologies such as micro fuel cells may provide the power to mobile device 100.

Microprocessor 102, in addition to its operating system functions, enables execution of software applications on mobile device 100. A set of applications that control basic device operations, including data and voice communication applications, will normally be installed on mobile device 100 during its manufacture. Another application that may be loaded onto mobile device 100 would be a personal information manager (PIM). A PIM has functionality to organize and manage data items of interest to a subscriber, such as, but not limited to, e-mail, calendar events, voice mails, appointments, and task items. A PIM application has the ability to send and receive data items via wireless network 200. PIM data items may be seamlessly integrated, synchronized, and updated via wireless network 200 with the mobile device subscriber's corresponding data items stored and/or associated with a host computer system. This functionality creates a mirrored host computer on mobile device 100 with respect to such items. This can be particularly advantageous where the host computer system is the mobile device subscriber's office computer system.

Additional applications may also be loaded onto mobile device 100 through network 200, auxiliary I/O subsystem 112, serial port 114, short-range communications subsystem 122, or any other suitable subsystem 124. This flexibility in application installation increases the functionality of mobile device 100 and may provide enhanced on-device functions, communication-related functions, or both. For example, secure communication applications may enable electronic commerce functions and other such financial transactions to be performed using mobile device 100.

Serial port 114 enables a subscriber to set preferences through an external device or software application and extends the capabilities of mobile device 100 by providing for information or software downloads to mobile device 100 other than through a wireless communication network. The alternate download path may, for example, be used to load an encryption key onto mobile device 100 through a direct and thus reliable and trusted connection to provide secure device communication.

Short-range communications subsystem 122 provides for communication between mobile device 100 and different systems or devices, without the use of network 200. For example, subsystem 122 may include an infrared device and associated circuits and components for short-range communication. Examples of short range communication would include standards developed by the Infrared Data Association (IrDA), Bluetooth, and the 802.11 family of standards developed by IEEE.

In use, a received signal such as a text message, an e-mail message, or web page download will be processed by communication subsystem 104 and input to microprocessor 102. Microprocessor 102 will then process the received signal for output to display 110 or alternatively to auxiliary I/O subsystem 112. A subscriber may also compose data items, such as e-mail messages, for example, using keyboard 116 in conjunction with display 110 and possibly auxiliary I/O subsystem 112. Auxiliary subsystem 112 may include devices such as: a touch screen, mouse, track ball, infrared fingerprint detector, or a roller wheel with dynamic button pressing capability. Keyboard 116 is an alphanumeric keyboard and/or telephone-type keypad, and may comprise physical buttons or keys and/or soft keys displayed on the display 110. A composed item may be transmitted over network 200 through communication subsystem 104.

For voice communications, the overall operation of mobile device 100 is substantially similar, except that the received signals would be output to speaker 118, and signals for transmission would be generated by microphone 120. Alternative voice or audio I/O subsystems, such as a voice message recording subsystem, may also be implemented on mobile device 100. Although voice or audio signal output is accomplished primarily through speaker 118, display 110 may also be used to provide additional information such as the identity of a calling party, duration of a voice call, or other voice call related information.

Referring now to FIG. 2, a block diagram of the communication subsystem component 104 of FIG. 1 is shown. Communication subsystem 104 comprises a receiver 150, a transmitter 152, one or more embedded or internal antenna elements 154, 156, Local Oscillators (LOs) 158, and a processing module such as a Digital Signal Processor (DSP) 160.

The particular design of communication subsystem 104 is dependent upon the network 200 in which mobile device 100 is intended to operate, thus it should be understood that the design illustrated in FIG. 2 serves only as one example. Signals received by antenna 154 through network 200 are input to receiver 150, which may perform such common receiver functions as signal amplification, frequency down conversion, filtering, channel selection, and analog-to-digital (A/D) conversion. A/D conversion of a received signal allows more complex communication functions such as demodulation and decoding to be performed in DSP 160. In a similar manner, signals to be transmitted are processed, including modulation and encoding, by DSP 160. These DSP-processed signals are input to transmitter 152 for digital-to-analog (D/A) conversion, frequency up conversion, filtering, amplification and transmission over network 200 via antenna 156. DSP 160 not only processes communication signals, but also provides for receiver and transmitter control. For example, the gains applied to communication signals in receiver 150 and transmitter 152 may be adaptively controlled through automatic gain control algorithms implemented in DSP 160.

The wireless link between mobile device 100 and a network 200 may contain one or more different channels, typically different RF channels, and associated protocols used between mobile device 100 and network 200. A RF channel is a limited resource that must be conserved, typically due to limits in overall bandwidth and limited battery power of mobile device 100.

When mobile device 100 is fully operational, transmitter 152 is typically keyed or turned on only when it is sending to network 200 and is otherwise turned off to conserve resources. Similarly, receiver 150 is periodically turned off to conserve power until it is needed to receive signals or information (if at all) during designated time periods.

Referring now to FIG. 3, a block diagram of a node of a wireless network is shown as 202. In practice, network 200 comprises one or more nodes 202. Mobile device 100 communicates with a node 202 within wireless network 200. In the example implementation of FIG. 3, node 202 is configured in accordance with General Packet Radio Service (GPRS) and Global Systems for Mobile (GSM) technologies. Node 202 includes a base station controller (BSC) 204 with an associated tower station 206, a Packet Control Unit (PCU) 208 added for GPRS support in GSM, a Mobile Switching Center (MSC) 210, a Home Location Register (HLR) 212, a Visitor Location Registry (VLR) 214, a Serving GPRS Support Node (SGSN) 216, a Gateway GPRS Support Node (GGSN) 218, and a Dynamic Host Configuration Protocol (DHCP) 220. This list of components is not meant to be an exhaustive list of the components of every node 202 within a GSM/GPRS network, but rather a list of components that are commonly used in communications through network 200.

In a GSM network, MSC 210 is coupled to BSC 204 and to a landline network, such as a Public Switched Telephone Network (PSTN) 222 to satisfy circuit switched requirements. The connection through PCU 208, SGSN 216 and GGSN 218 to the public or private network (Internet) 224 (also referred to herein generally as a shared network infrastructure) represents the data path for GPRS capable mobile devices. In a GSM network extended with GPRS capabilities, BSC 204 also contains a Packet Control Unit (PCU) 208 that connects to SGSN 216 to control segmentation, radio channel allocation and to satisfy packet switched requirements. To track mobile device location and availability for both circuit switched and packet switched management, HLR 212 is shared between MSC 210 and SGSN 216. Access to VLR 214 is controlled by MSC 210.

Station 206 is a fixed transceiver station. Station 206 and BSC 204 together form the fixed transceiver equipment. The fixed transceiver equipment provides wireless network coverage for a particular coverage area commonly referred to as a “cell”. The fixed transceiver equipment transmits communication signals to and receives communication signals from mobile devices within its cell via station 206. The fixed transceiver equipment normally performs such functions as modulation and possibly encoding and/or encryption of signals to be transmitted to the mobile device in accordance with particular, usually predetermined, communication protocols and parameters, under control of its controller. The fixed transceiver equipment similarly demodulates and possibly decodes and decrypts, if necessary, any communication signals received from mobile device 100 within its cell. Communication protocols and parameters may vary between different nodes. For example, one node may employ a different modulation scheme and operate at different frequencies than other nodes.

For all mobile devices 100 registered with a specific network, permanent configuration data such as a user profile is stored in HLR 212. HLR 212 also contains location information for each registered mobile device and can be queried to determine the current location of a mobile device. MSC 210 is responsible for a group of location areas and stores the data of the mobile devices currently in its area of responsibility in VLR 214. Further VLR 214 also contains information on mobile devices that are visiting other networks. The information in VLR 214 includes part of the permanent mobile device data transmitted from HLR 212 to VLR 214 for faster access. By moving additional information from a remote HLR 212 node to VLR 214, the amount of traffic between these nodes can be reduced so that voice and data services can be provided with faster response times and at the same time requiring less use of computing resources.

SGSN 216 and GGSN 218 are elements added for GPRS support; namely packet switched data support, within GSM. SGSN 216 and MSC 210 have similar responsibilities within wireless network 200 by keeping track of the location of each mobile device 100. SGSN 216 also performs security functions and access control for data traffic on network 200. GGSN 218 provides internetworking connections with external packet switched networks and connects to one or more SGSNs 216 via an Internet Protocol (IP) backbone network operated within the network 200. During normal operations, a given mobile device 100 must perform a “GPRS Attach” to acquire an IP address and to access data services. This requirement is not present in circuit switched voice channels as Integrated Services Digital Network (ISDN) addresses are used for routing incoming and outgoing calls. Currently, all GPRS capable networks use private, dynamically assigned IP addresses, thus requiring a DHCP server 220 connected to the GGSN 218. There are many mechanisms for dynamic IP assignment, including using a combination of a Remote Authentication Dial-In User Service (RADIUS) server and DHCP server. Once the GPRS Attach is complete, a logical connection is established from a mobile device 100, through PCU 208, and SGSN 216 to an Access Point Node (APN) within GGSN 218. The APN represents a logical end of an IP tunnel that can either access direct Internet compatible services or private network connections. The APN also represents a security mechanism for network 200, insofar as each mobile device 100 must be assigned to one or more APNs and mobile devices 100 cannot exchange data without first performing a GPRS Attach to an APN that it has been authorized to use. The APN may be considered to be similar to an Internet domain name such as “myconnection.wireless.com”.

Once the GPRS Attach is complete, a tunnel is created and all traffic is exchanged within standard IP packets using any protocol that can be supported in IP packets. This includes tunneling methods such as IP over IP as in the case with some IPSecurity (IPsec) connections used with Virtual Private Networks (VPN). These tunnels are also referred to as Packet Data Protocol (PDP) Contexts and there are a limited number of these available in the network 200. To maximize use of the PDP Contexts, network 200 will run an idle timer for each PDP Context to determine if there is a lack of activity. When a mobile device 100 is not using its PDP Context, the PDP Context can be de-allocated and the IP address returned to the IP address pool managed by DHCP server 220.

Referring now to FIG. 4, a block diagram illustrating further aspects of mobile device 100 of FIG. 1 is shown generally as 300. As noted earlier with reference to FIG. 1, microprocessor 102, in addition to its operating system functions, enables execution of software applications on mobile device 100. A set of applications that control basic device operations, including data and voice communication applications, will normally be installed on mobile device 100 during its manufacture. Operating system software and other software applications are typically stored in a persistent store (e.g. flash memory 108) or other store, on mobile device 100 or on a device coupled thereto. It will be understood that the operating system, software applications or parts thereof, may be temporarily loaded in a volatile store such as RAM 106. Other instructions and/or data received by the mobile device 100 and subject to processing may also be temporarily stored in RAM 106.

Software applications that are loaded or stored on mobile device 100 may be implemented as functional components or modules 310. Modules 310 interact with various components of mobile device 100. For instance, as shown by way of example in FIG. 4, modules 310 may interact with communication subsystem 104, RAM 106, flash memory 108, display 110, auxiliary I/O device(s) 112, and keyboard 116. Modules 310 may comprise, for example, an address book module 312, a messaging module 314 (e.g. for e-mail and/or SMS or MMS messaging), phone application module 316, and a call log module 317.

Address book module 312 is generally configured to allow contact information (e.g. individual contact and company names, telephone numbers, messaging addresses, and other information) to be stored and managed. Messaging module 314 facilitates the sending and receiving of electronic messages over a wireless network 200 and/or other network.

Phone application module 316 is generally configured to facilitate voice communication between the user and other parties, including the placement of outgoing calls by the user and the reception of incoming calls on the mobile device 100. Call log module 317 is generally configured to store and manage calling activity data (for example, time and date of incoming or outgoing calls, and third party phone numbers involved in such calls).

Calls may be placed and received on a communication line specifically configured for voice communications. In certain embodiments, calls may alternatively or additionally be placed and received on other types of communication lines, including a communication line generally configured for data communications, or a communication line configured for both voice and data communications, for example. For example, mobile device 100 may be configured to provide Voice over IP (VoIP), Enterprise Voice, and/or video phone functionality.

Embodiments described herein are generally applicable to mobile devices that provide access to multiple (i.e. two or more) communication lines on which outgoing calls may be placed, as initiated by a mobile device user. Typically, these mobile devices will also be configured to allow incoming calls to be received by the user over the same communication lines.

In example embodiments, each of the multiple communication lines has a different telephone number associated therewith. For example, a user may have a business phone number and a different personal phone number. When a user places an outgoing call on a specific communication line, the phone number associated with that communication line may be identified on a receiving party's phone that is equipped with “call display” functionality.

Referring again to FIG. 4, a line selection module (e.g. alternate line service (ALS) module) 318 is provided to facilitate selection of the communication line to be used by phone application module 316 for placing an outgoing call, for example. The line selection module 318 is configured to select a communication line to be used by phone application module 316, based upon line selection data stored on mobile device 100 (e.g. configuration settings that define a default communication line), and/or based upon input received by the user. It will be understood that the functionality of line selection module 318 may be provided or otherwise integrated with phone application module 316 or with a different module on mobile device 100.

The currently selected communication line on which an outgoing call may be placed at any given time is also referred to herein as the “active” line. Outgoing calls will be placed on the active line by phone application module 316 until an alternate communication line is selected.

When a user wishes to initiate an outgoing call, the user will typically be required to access a call screen provided by an application (e.g. phone application module 316) on mobile device 100. Data identifying the active line will be displayed to the user in a first display field (e.g. “My Number” field, or phone status field) of the call screen, allowing the user to quickly identify the communication line on which an outgoing call will be placed should the user choose to initiate such call. This display field may also be referred to as an active line data display field. The data identifying the active line typically comprises a telephone number, but may alternatively or additionally comprise some other communication line identifier(s), such as a line descriptor, alias and/or other identifier, for example.

Should the user wish to initiate an outgoing call to be placed on an alternate communication line, the user may need to change the current active line using a different application or in a separate screen, and then return to the call screen to place the call on the alternate communication line after the change is made.

A calling card management module 320 is also provided (which interacts with the line selection module 318), to facilitate selection of a calling card to be used by phone application module 316 when placing an outgoing call, for example. A calling card database 322 is also provided, which is configured to store calling card data records 324, each record 324 containing calling card data corresponding to one of the calling cards in a set of at least one calling card.

The calling card management module 320 is configured to associate each calling card to a communication line which may be used by the phone application module 316 (and particularly by the line selection module 318) in placing an outgoing call. The selection of a particular calling card (if one is to be used in a particular call) may be based upon card/line selection data stored on mobile device 100 (e.g. configuration settings that define a default communication card/line combination), and/or based upon input received by the user. It will be understood that the functionality of line selection module 318 may be provided or otherwise integrated with phone application module 316 or with a different module on mobile device 100.

It will also be understood that the calling card management module 320 may be configured to operate seamlessly with the line selection module 318 such that the selection of a calling card and a line to be used in making an outgoing call may be done in a single step (of selecting a card/line combination) at the time of placing a call (if the default card/line combination needs to be changed).

Referring to FIG. 5, illustrated therein is exemplary data as may be stored in calling card records 324 in the calling card database 322. At least one calling card record 324 is created for each calling card 506 in the set of available calling cards 506. Each record 324 may store line identifier data 502 identifying one of the outgoing lines managed by the line selection module 318, together with a unique calling card/line identifier 504 to be used in identifying the card/line combination. Any suitable alias or other identifier may be input by the user and stored as the identifier—some identifiers 504 may expressly identify both the calling card and the communication line, but this may not be necessary (for example, if the calling card is the user's “work” calling card, which is assigned to the “work” line, and in such case identifying the “work” calling card may be sufficient). Each record 324 will also include a phone number 506 associated with the calling card, to be called when initiating the calling card service, and authentication data 508 (often in the form of a password, but which may also include account numbers, etc.) which may be required by (and hence, communicated to) the calling card service for authentication. In the exemplary data, two different calling cards 506 in the set are combined with the same outgoing line 502 (“Line No. 1”). However, it should also be understood that a calling card 506 may be associated with more than one outgoing line 502. For example, if the mobile device 100 is provided with multiple “work” related lines, the same “work” calling card may be used for all such “work” lines.

Referring to FIG. 7D, illustrated therein is a screenshot of a user interface screen 760 as may be presented to a user and showing the exemplary calling card records 324 data of FIG. 5 as may be stored in the calling card database 322. The user may also cause a pop-up calling card modification menu 770 to be displayed. For example, the user may depress or otherwise select the menu key 771 while the calling card screen 760 is displayed, to cause the calling card modification menu 770 to be displayed and enable the user to “Add” 772 new calling card record 324 data or otherwise modify and “Save” 774 calling card record 324 data. As will be understood, the menu key 771 may be in the form of a physical button or keys or be a soft key displayed on the display 110.

Referring now to FIG. 6, a flowchart illustrating steps of a method in accordance with at least one embodiment, is shown generally as 600. The method is performed on a mobile device having a plurality of communication lines on which outgoing calls may be made, and provides a user interface for selecting an outgoing line on which outgoing calls may be made and a calling card to be used (if any) in making an outgoing call to a desired phone number. The set of at least one calling card is provided and the corresponding calling card data is stored in the calling card records 324 as discussed above in relation to FIG. 5. Additional details of some of the features described below in respect of the steps of method 600 may be described elsewhere in the present specification. Referring now also to FIGS. 7A to 7C, illustrated therein are screenshots of a user interface provided to a user in one example implementation of an embodiment of the method of FIG. 6.

In one embodiment, the steps of method 600 are performed at the mobile device by an application (e.g. phone application module 316 of FIG. 4) that typically executes and resides on the CPU of the mobile device (e.g. mobile device 100 of FIG. 1). The application need not be a stand-alone application, and the functionality described herein may be implemented in one or more applications executing and residing on the mobile device 100.

At Block 610 (shown in FIG. 6), a call screen (such as screen 700 illustrated in FIG. 7A) is displayed to the user on a display (e.g. display 110 of FIG. 1) of the mobile device 100. A user may access the call screen when the user wishes to initiate an outgoing call. This may require first activating a phone application or other application on the mobile device 100, by selecting a corresponding item or icon from a menu or home screen, for example (such as phone button 701). As noted previously, the mobile device 100 provides access to multiple communication lines on which outgoing calls may be placed.

In FIG. 7A, screenshot 700 illustrates a user interface displayed in a display 110 of a mobile device 100 (shown in FIG. 1), namely a call screen from which the user can place outgoing calls. Call screen 700 is displayed to the user, awaiting user input (e.g. a number to be dialed). A number entry field 702 is provided, and cursor 704 is settled within number entry field 702, indicating that the user may provide a call number (e.g. using a keyboard or keypad). General indicators may be displayed on call screen 700, including for example, time 706, date (not shown), network indicator 710, signal strength 712, battery strength 714, alarm indicator (not shown), service provider indicator (not shown), ringer indicator (not shown), and/or Bluetooth™ indicator (not shown).

A first line identifier 740 identifying a first of the multiple calling card/communication line combinations available on the mobile device 100 is displayed in a first display field 742 (“active calling card/line display field”) of the call screen 700. The first display field 742 may be referred to as a “My Number” field or a “phone status” field, and data 740 displayed therein identifies the active line and calling card combination, allowing the user to quickly identify the line on which an outgoing call will be placed and a calling card which will be used should the user choose to initiate such a call.

The data 740 identifying the active calling card/outgoing line combination may comprise a telephone number associated with the active calling card/line, but may alternatively or additionally comprise some other calling card/line identifier(s), such as, for example, one or more aliases, identifiers and/or other descriptors (e.g. “Mobile Line”, “Work Line”, “Alternate Line”), which may be user-defined.

At Block 612 (shown in FIG. 6), the mobile device 100 may scan or wait for call screen interaction by the user. As will be understood, such scanning or writing may be active or passive.

Subsequently, an input or other call screen interaction by the user may be detected. For example, such call screen interaction may involve the movement of a selection element (e.g. a highlight bar, pointer, cursor 704, or other means to identify and select menu or list items). The selection element may be re-positioned at the direction of the user, using an input device such as a thumb wheel, track ball, keyboard, mouse, touchpad or other input device. For example, the user may use a track ball on the mobile device 100, where provided, to manipulate a highlight bar shown in the call screen 600.

Alternatively, call screen interaction may be detected when a selection element (e.g. a highlight bar, pointer, cursor 704, or other means to identify and select menu or list items) displayed on the call screen 700 has been moved into the first display field 742. For example, by rotating the track ball, a highlight bar may be re-positioned to highlight the data 740 displayed in the first display field 742 (e.g. the telephone number associated with the active line) of the call screen 700. Alternatively, the detected call screen interaction may involve movement of a selection element into the outgoing call input or number entry field 702. Yet other call screen interaction which may be detected for example may involve the inputting of a telephone number in the number entry field 702 by the user in order to initiate an outgoing call.

At Block 614 (shown in FIG. 6), in some embodiments upon detection of call screen interaction, as illustrated in FIG. 7B, a line selection menu 750 is displayed on the display. The line selection menu 750 comprises a plurality of card/line identifiers 740, each uniquely identifying a corresponding combination of a communication line on which the user may place or make an outgoing call (or receive an incoming call) and calling card 324 to be used in making any outgoing call. Card/line identifiers 740 identifying at least a subset of the multiple communication line/calling card combinations available on the mobile device 100 (including “combinations” in which no calling card is identified) are displayed on the line selection menu 750. In the example illustrated in FIG. 7B, the line selection menu 750 identifies communication lines “Line 1” and “Line 2” which are not combined with a calling card (and hence, if selected, would not utilize a calling card for outgoing calls), together with various other exemplary calling card/line combinations discussed previously with respect to the calling card records 324 illustrated in FIG. 5 available on the example embodiment of the mobile device 100.

In some embodiments, as an alternative to immediately displaying the line selection menu 750 upon detection of call screen interaction, at Block 613 (shown in FIG. 6), the call screen 700 might first prompt for a line change instruction. In order for the line selection menu 750 to be displayed at Block 614 (shown in FIG. 6), the user may then input a “change line” (or “change card/line”) command. For example, the user may depress the track wheel or track ball while a “Change Line” comment is displayed, to enter the “change line command” and cause the line selection menu 650 to be displayed.

At Block 616 (shown in FIG. 6), the user may select an alternate card/communication line combination. A selection element (e.g. a highlight bar, pointer, cursor, or other means to identify and select menu or list items) may be displayed within the line selection menu 750 and may be repositioned at the direction of the user, using an input device such as a thumb wheel, track ball, keyboard, mouse, touch pad, touch screen or other input device. For example, the user may use a track ball on mobile device 100, where provided, to manipulate a highlight bar shown in the display 110. In particular, by rotating the track ball in this example, the highlight bar may be re-positioned to highlight the line identifier 740 associated with a particular communication line/card combination displayed in the line selection menu 750. Once the user highlights a desired communication line/card combination, by manipulating the track ball so that the highlight bar settles on the corresponding card/line identifier 740, the user may then take further action. For example, the user may depress the track ball to select the desired calling card/communication line combination.

At Block 618 (shown in FIG. 6), upon selection of a different calling card/communication line combination, the first display field 742 is updated with data 740 identifying the user-selected calling card/communication line combination. Accordingly, the user-selected calling card/communication line combination is identified to the user as the current active “line” on which outgoing calls will be placed (and calling card to be used, if any). In the example illustrated in FIG. 7C, the “Personal Calling Card” calling card/line combination (as identified in FIG. 5) has been selected in Block 616 (shown in FIG. 6), which has become the currently active line on which outgoing calls will be placed (and calling card will be used as necessary).

At Block 620 (shown in FIG. 6), the telephone call is initiated on the active communication line (of the active calling card/line combination), via the appropriate calling card service. As previously noted, the user may input (or otherwise cause the mobile device 100 to receive) the desired telephone number of the party the user wishes to call (Block 622), for example by manually entering the telephone number within the number entry field 702 or by selecting a previously stored number utilizing the address book module 312.

At Block 624, the phone application module 316 may place a call to the calling card service, if necessary, by placing a call to the calling card phone number 506 of the calling card 504 in the active calling card/line combination, on the corresponding outgoing line. The phone application module 316 may be programmed to determine if use of a calling card service is not required (eg. if the phone call is to a local exchange). At Block 626, the phone application module 316 may then communicate any required authentication data 508 to the calling card service over the telephone call. At Block 628, the phone application module 316 may also communicate the desired telephone number of the party the user wishes to call to the calling card service over the telephone call, so that the calling card service may establish the necessary communication link to the desired telephone number. As illustrated by the dotted line, in some embodiments or instances, the user may initiate a call as discussed in relation to Block 620, without changing the previously-determined active calling card/line combination (discussed in relation to Blocks 616-618).

In some embodiments, the calling card/line combination 740 and phone application module 316/calling card management module 320 may be configured to enable other applications to transparently initiate outgoing long-distance phone calls on the active “line” (representing a card/line combination 740) without such other applications needing to “know” that (or be configured to utilize) a calling card service will be used in making such a call. Accordingly, a call may be initiated from an address book, speed dial, voice activated dialing, document hyperlink or external car kit, and any such call will utilize the calling card/line combination 740. As will be understood, the phone application module 316/calling card management module 320 may be configured such that users may not be required to implement (and hence learn) a different calling procedure to implement a “calling card” call as contrasted with implementing a non-calling card call. Further a user is not required to access a separate or additional “calling card” application (in addition to a phone application) if a calling card is to be used.

It will be understood by persons skilled in the art that the features of the user interfaces illustrated with reference to the example screenshots described herein are provided by way of example only. It will be understood by persons skilled in the art that variations are possible in variant implementations and embodiments.

The steps of a method of providing a user interface that facilitates user selection of a communication line for an outgoing call on a mobile device in accordance with any of the embodiments described herein may be provided as executable software instructions stored on computer-readable media, which may include transmission-type media.

The disclosure has been described with regard to a number of embodiments. However, it will be understood by persons skilled in the art that other variants and modifications may be made without departing from the scope of the disclosure as defined in the claims appended hereto. 

1. A method of, on a mobile device having a plurality of communication lines on which outgoing calls may be made, providing a user interface for selecting a calling card to be used in making an outgoing call to a desired phone number, the method comprising: a) associating each calling card in a set of at least one calling card with a communication line; b) displaying on a display of the mobile device a line selection menu containing a plurality of card/line identifiers; c) wherein each card/line identifier is configured to uniquely identify a corresponding associated calling card and communication line combination.
 2. The method of claim 1, further comprising: a) selecting one of the card/line identifiers; b) receiving the desired phone number; c) initiating an outgoing call in connection with the selected card/line identifier.
 3. The method of claim 1, further comprising: a) storing calling card data corresponding to each calling card.
 4. The method of claim 3, wherein the calling card data corresponding to each calling card comprises: a) a calling card phone number; and b) authentication data.
 5. The method of claim 4, wherein initiating the outgoing call comprises: a) placing a call to the calling card phone number corresponding to the selected card/line identifier; b) wherein the call is placed on the communication line corresponding to the selected card/line identifier; c) communicating the corresponding authentication data over the communication line corresponding to the selected card/line identifier; and d) communicating the desired phone number over the communication line corresponding to the selected card/line identifier.
 6. A computer-readable medium comprising instructions executable on a processor of the mobile device for implementing the method of claim
 1. 7. A mobile device configured to provide a user interface for selecting a calling card to be used in making an outgoing call to a desired phone number, the mobile device providing access to a plurality of communication lines on which outgoing calls may be made, the mobile device comprising a processor, a display, and at least one input device, wherein the processor is configured to execute an application programmed to perform the steps of the method as claimed in claim
 1. 8. A system for providing a user interface for selecting a calling card to be used in making an outgoing call to a desired phone number, the system comprising: a plurality of communication lines on which outgoing calls may be made, a processor, a display, and at least one input device, wherein the processor is configured to execute an application programmed to perform the method as claimed in claim
 1. 9. A mobile device comprising a processor, a display, and at least one input device, wherein the mobile device is configured to access a plurality of communication lines, and wherein the processor is configured to perform the steps of: a) associating each calling card in a set of at least one calling card with a communication line; b) displaying on the display a line selection menu containing a plurality of card/line identifiers; c) wherein each card/line identifier is configured to uniquely identify a corresponding associated calling card and communication line combination.
 10. The device as claimed in claim 9, further comprising a calling card database configured to store calling card data corresponding to each calling card in the set.
 11. The device as claimed in claim 10, wherein the calling card data corresponding to each calling card comprises: a) a calling card phone number; and b) authentication data.
 12. The device as claimed in claim 11, wherein upon receiving input corresponding to a selection of one of the line identifiers and upon receiving a desired phone number, the processor is further configured to: a) place a call to the calling card phone number corresponding to the selected card/line identifier; and b) wherein the call is placed on the communication line corresponding to the selected card/line identifier.
 13. The device as claimed in claim 12, wherein upon receiving input corresponding to a selection of one of the line identifiers and upon receiving a desired phone number, the processor is further configured to: c) communicate the corresponding authentication data over the communication line corresponding to the selected card/line identifier.
 14. The device as claimed in claim 13, wherein upon receiving input corresponding to a selection of one of the line identifiers and upon receiving a desired phone number, the processor is further configured to: d) communicate the desired phone number over the communication line corresponding to the selected card/line identifier. 